Integration with Gelato (deprecated)
Relaying transactions through Gelato is no longer supported.
From September 1, 2026, transactions can't be relayed through Gelato using
the Relay Kit. This affects the GelatoRelayPack, including both the Gelato
1Balance and the Gelato SyncFee flows.
If your integration relies on the GelatoRelayPack, migrate to the
ERC-4337 Safe SDK guide, which uses the Safe4337Pack
to sponsor transactions or pay fees in ERC-20 tokens through a paymaster.
What changed
The Relay Kit previously shipped two ways to relay a Safe transaction through Gelato:
- Gelato 1Balance, which sponsored transactions from a prepaid deposit.
- Gelato SyncFee, which paid the gas fees directly with funds held in the Safe account.
Neither flow is supported anymore. The code examples previously published on this page have been removed so they aren't copied into new integrations.
What to use instead
The Safe4337Pack covers the same use cases through the
ERC-4337 standard:
| Previous Gelato flow | ERC-4337 equivalent |
|---|---|
| 1Balance (sponsored transactions) | A verifying paymaster configured with paymasterOptions |
| SyncFee (pay fees from the Safe balance) | An ERC-20 paymaster configured with paymasterOptions |
See the ERC-4337 Safe SDK guide for a complete example,
and the Safe4337Pack reference for the full
API.
Differences
The ERC-4337 flow covers the same use cases, but is not a drop-in substitute. Before you start rewriting note these differences:
- No cross-chain sponsoring: With the Gelato flow you could sponsor cross-chain, using a deposit on one chain sponsoring a transaction on another. This feature is not available on the ERC-4337 flow. You have to fund the paymaster per chain.
- Chain Availability: The ERC-4337 module is deployed on a different
chain set than the previous flow. On chains where it is not deployed,
init()will throw. The official module deployments (opens in a new tab) lists the chains where it is deployed. - Safe ≥ v1.4.1: The ERC-4337 flow is supported for Safe v1.4.1 and higher.